G|Vis ???<br><br>When is a newer version of G|Vis that can <br>handel larger blockmaps and levels that<br>are larger than 5 MB and consist of < 20,000<br>Sectors going to be released?<br><br>What params would I have to change to make<br>G|Vis work with larger levels--or are u going to<br>make a linked version of G|Vis that does not depend<br>on level size but on the amount of memory avail.<br><br>How can I tell if G|Vis is freezing or just taking it's time<br>working--it always halts on 16xx and starts from<br>15xxx in it's count down--it goes blazingly fast until<br>it gets to count 8xxx and then it starts to take it's <br>sweet old time                   <br><br>why ???<br><br><br>Thank you &  :) may the pizza b /w u  :)<br><br>Lionel Hutz  :) Attny. @ Law  :)<br><br>PS<br> <!-- s:) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" /><!-- s:) --> <!-- s;) --><img src="{SMILIES_PATH}/icon_wink.gif" alt=";)" title="Wink" /><!-- s;) --> ;D Remember to Watch the Simpsons on FOXTV<br> <!-- s:) --><img src="{SMILIES_PATH}/icon_smile.gif" alt=":)" title="Smile" /><!-- s:) --> <!-- s;) --><img src="{SMILIES_PATH}/icon_wink.gif" alt=";)" title="Wink" /><!-- s;) --> ;D<br><br>BECAUSE<br><br>it's  8) k00| <!-- s8) --><img src="{SMILIES_PATH}/icon_cool.gif" alt="8)" title="Cool" /><!-- s8) -->

I haven't found why it freezes. It shouldn't depend on level size at all. A larger level should simply take more memory and that's all. But when I will find something, I will release it.

You sure this is freezing that we're speaking of?<br><br>I know that really complicated stuff DOES take a while for it to break down, just does.<br><br>And it DOES get slower as the count goes down it seems.<br><br>I'd imagine that's because of increasingly complicated data structures as it goes along?

You sure this is freezing that we're speaking of?

<br>Most likely it really freezes.<br><br>

And it DOES get slower as the count goes down it seems.<br><br>I'd imagine that's because of increasingly complicated data structures as it goes along?

<br>In first phase segment records a number of other segments needed to be checked with, and in second phase they are processed in this sorted order.<br>

???<br><br>Is their any type of error checking I could<br>add to glVis to attempt  8) to find out where<br>& why it crashes.<br><br>How could I get glVis to generate a Stack Trace<br>so I could figure out how to repair the functions<br>or post the offending function onto this forum.<br><br>Thank you,<br><br>L.H.

You could modify glVIS to print some message when doing each step. It isn't hard to add stack traces when it crashes., all you need to do as add try/catch blocks and a signal handler which throws an exception.